Repository navigation
chore: CI checks the documents' links and private data (gate job ci); the profile points at overpressure's releases - #3
Merged
Conversation
… job, ci; the profile points at overpressure's releases
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
This repository had no CI, while its CONTRIBUTING says a pull request is merged once its checks pass.
links: lychee, pinned, checks every link of the Markdown files. The profile and the default community files link into the other repositories, whose files can move.private: overpressure'scheck-private.py --history.ci, fails unless both passed. It becomes the required check once this is onmain.Checks
check-private.py --repo . --history)Hardware
Not needed. Not run on GitHub yet: this PR's run is the first.